cboj-payments-prc-api

Description:

This API fteches summary of standing order using Customer id.

This API has the flexibility of following ACTIONs:

VALIDATE: A transfer request can be validated using VALIDATE action, which returns either a success / error response after validating the request. This is useful to correct the data if any before the actual fund transfer. Any VALIDATE action request will not update / process the backed Temenos system.

PROCESS: Once a request is validated / re-validated successfully using VALIDATE action, a request can then be sent for PROCESS action. This action actually transfers the required fund / amount from the respective accounts, if no authorization is required. If authorization is enabled , the PROCESS action sends the fund transfer request to the authorizer for authorization post which the actual fund transfer takes place.

AMEND: If any changes or modifications are required before processing the transfer , an AMEND action can be used for the same. AMEND action is similar to PROCESS action. The only difference is that the FT Reference ID (a unique transaction id received in response during PROCESS action), should be sent as a mandatory element, while other elements can be optional except for the modifiable field. This AMEND action works only until the record is Authorized. Once the record is Authorized, AMEND doesn't work.

DELETE: Any fund transfer request which is pending for authorization can be deleted using this action. FT reference number is mandatory for this action.

AUTHORIZE: Any fund transfer request which is pending for authorization can be authorized using this action. Unless a record is authorized , the actual fund transfer does not occur in the temenos core banking. Except for the FT reference number no other fields are required for authorization requests.

Mulesoft Request:

Headers:

Mandatory Headers: x-channel-id,x-client-trace-id, x-bank-id,client_id, client_secret

Optional Headers: x-sub-channel-id,x-user-id, Authorization, x-debug-flag, x-customer-id

Paramaters:

URI Params: Customer id

Query Params: NA

Content-type: application/json

Body:

```

NA

Mulesoft Response:

Success Response: (200)

 {
    "standingOrders": [
        {
            "ftReference": "4000091.10",
            "senderAccountNo": "JO70EFBK0010000000000004000091",
            "recieverAccountNo": "JO91EFBK0010000000000004175283",
            "currency": "USD",
            "amount": "100.00",
            "frequency": "Monthly",
            "transferDate": "20210301"
        },
        {
            "ftReference": "4000218.1",
            "senderName": "SecondChange",
            "senderAccountNo": "JO36EFBK0010000000000004000218",
            "recieverAccountNo": "1000006",
            "currency": "JOD",
            "amount": "1.000",
            "frequency": "Every working day",
            "transferDate": "20201115"
        },
        {
            "ftReference": "4000218.2",
            "senderName": "SecondChange",
            "senderAccountNo": "JO36EFBK0010000000000004000218",
            "recieverAccountNo": "1000006",
            "currency": "JOD",
            "amount": "101.000",
            "frequency": "Daily",
            "transferDate": "20220531"
        }

        ],
    "status": {
        "success": true,
        "code": "200",
        "arabicMessage": "تمت العملية بنجاح",
        "englishMessage": "The Operation has been Successfully Completed"
    }
}

```

```

Sample Error Response:

Please refer the HOME page for all possible combinations of error response codes.

Note: The 'errorCode' and 'backendErrorMessage' will be in the error response message only if 'x-debug-flag' is '1'

400 :

{

"status": {

    "success": false,

    "code": "T24003799",

    "reasonCode": "BadRequest",

    "arabicMessage": "NO SIGN ON NAME SUPPLIED DURING SIGN ON PROCESS",

    "englishMessage": "NO SIGN ON NAME SUPPLIED DURING SIGN ON PROCESS",

    "errorCode": "T24003799",

    "errorDescription": "INVALID/ NO SIGN ON NAME SUPPLIED DURING SIGN ON PROCESS"

}

}

```